Columbia Kermit/kermit.zip/newsgroups/misc.19970104-19970326/[e-mail] _Wed Feb 19 07:05:31 1997.msg

Internet Message Format | 2020-01-01 | 5KB

Return-Path: <[e-mail]>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
    by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id HAA21672
    for <[e-mail]>; Wed, 19 Feb 1997 07:05:30 -0500 (EST)
Received: (from news@localhost)
    by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id HAA26717
    for kermit.misc@watsun; Wed, 19 Feb 1997 07:05:29 -0500 (EST)
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!panix!news.mathworks.com!news.maxwell.syr.edu!insync!uunet!in2.uu.net!204.74.114.90!news.genuity.net!news.lafn.org!lafn.org!lafn.org!aw585
From: [e-mail] (Dallas Legan)
Subject: Re: OS/2 Specific DOS and MS-DOS Kermit
X-Nntp-Posting-Host: lafn.org
Message-ID: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail] (Dallas Legan)
Organization: The Los Angeles Free-Net
References: <1997Feb17.103511.155285@forest> <1997Feb15.090805.155151@forest>  <[e-mail]>
Date: Wed, 19 Feb 1997 11:08:30 GMT
Lines: 112
Xref: news.columbia.edu comp.protocols.kermit.misc:6621


In a previous article, [e-mail] (Paul Coen) says:

>In article <[e-mail]>, [e-mail] (Dallas Legan) writes:
>> I went back and added to
>> DEVICE=C:\OS2\BOOT\COM.SYS
>> to make it:
>> DEVICE=C:\OS2\BOOT\COM.SYS (3,3F8,4) (4,2E8,3)
>>
>
>Okay, that's good -- I'm sure that wasn't helping matters any.  However,
>you're using the same IRQ for COM4 as COM2 -- is anything else using
>COM2 at the same time?  .....................
>

No!  I've run this way under straight, plain vanilla DOS all the time
with no problems, and it run about the same in the DOS full screen
window in OS/2 now with the right settings dialed in, but still
will only work under the specific DOS if I comment out the OS/2 config.sys
drivers, and reboot before booting the specific DOS version.
Maybe this is a case of DOS being too dumb to know it was not
supposed to work this way, and the more sophisticated
operating system noticing something is wrong. Anyway, nothing is
hooked up to the other COM ports, and they are all set to the
defacto standards:

COM1   x3f8, IRQ 4
COM2   x2f8, IRQ 3
COM3   x3e8, IRQ 4
COM4   x2e8, IRQ 3

When run under plain DOS, MSD shows 1,2, &4 as 16550AF's, with
#3 as an 8250,
While under the Specific DOS session, MSD shows all of them as
16550AF's - I don't know if that matters or not.

>Anyway, you may need to tell MS-Kermit where it is, or where you
>put it.  The command is 'SET COM4 \x02e8 \3' (or whatever it actually
>is).

I usually do this in the MSCUSTOM.INI file.

>
>> and even added the
>> DEVICE=C:\OS2\MDOS\COMDD.SYS
>> which supposedly some software needs
>> (I don't know if I put it in the right position, or
>> even if the location in CONFIG.SYS matters?)
>>
>
>Order doesn't really matter.

Which I didn't know previously.

>
>>                                       AAAAAAAAAA-- no, it's not
>>                                          it's 3.0
>>
>
>RMVIEW should work anyway -- type RMVIEW /? to get the options (I

When run under OS/2, it agreed with what MSD showed under
straight DOS and in the Specific DOS booted session, and what is above.

>
>> Still, why not the Specific DOS?
>> (I like the COMMAND.COM that I'm using on it)
>> I found that commenting out all COM device drivers
>> in CONFIG.SYS - COM.SYS AND VCOM.SYS (and COMDD.SYS if that matters
>> any) enabled MS-DOS Kermit to run from a
>> Specific DOS session booted from a disk.
>> This seems extremely awkward, but maybe it provides someone
>> more knowledgable about OS/2 a clue as to what will work more
>> smoothly.  Somehow, I suspect maybe the VIO.SYS I've seen
>> mentioned might solve it, but I don't know.
>
>
>I think you mean "SIO.SYS" -- VIO is the PM API used to deal with text

Your right about this, my memory was getting confused!

>windows.  The only problem with a "specific DOS" is that it takes
>more system overhead.  Also, something is just not configured right
>if you have to do the above to get it to work -- I've been running
>MS-Kermit since OS/2 2.0 in an OS/2 DOS window with no problems.
>
>Anyway, SIO won't help in this situation -- I suspect you'll have the
>same sort of configuration problem, whatever it is.
>

I tried installing a version of COM.SYS I found on the HOBBES
archive CD-ROMS, that is a few months more recent then my system was
dated, to no avail.

Again, thanks!
Some might think this is a waste of time, but I've found that
trying to plow through problems like this frequently is worthwhile
in terms of understanding what is going on, and in this case will
probably result in my understanding OS/2, the Specific DOS boot process,
MS-DOS Kermit, and the PC communication port hardware better.
Already, studying over the documents for running MS-DOS Kermit
helped me to get it running properly in the full screen DOS windows,
which in turn helped me to run a FAX program I use a lot in them as well.
I'll probably get the OS/2 versions of C-Kermit running sometime not
too distant in the future, but in the meantime I can run my
MS-DOS Kermit scripts in the DOS windows without having to reboot to
DOS, and with a minimum of adaptations.

Regards,
Dallas E. Legan
562-862-4854 ext. '*'
[e-mail]